home *** CD-ROM | disk | FTP | other *** search
- Path: tomtec.abg.sub.org!judas
- From: judas@tomtec.abg.sub.org (Th.Huber)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Serial Cable
- Distribution: world
- Message-ID: <judas.0hqg@tomtec.abg.sub.org>
- References: <38231986@kone.fipnet.fi> <judas.0hi3@tomtec.abg.sub.org> <38232131@kone.fipnet.fi>
- Date: 29 Jan 96 12:28:37 MET
-
- In article <38232131@kone.fipnet.fi> "Jyrki Saarinen" <jsaarinen@kone.fipnet.fi> writes:
- >
-
- >> To go sure the blitter has finished, you just access chipram.
- >> (naaaahh, don`t tell me about waitblit() .. =)
- >
- >What? How the hell blitter state can be tested by accessing
- >chipmem?
-
- Yep. Making the blitter busy enough, there`s no free cycle to get anything
- from chipmem. You start the blitter, then read a word from chipmem, that`s it.
-
-
-
- >> As the AAchipset allows access to chipram, while blits are active, you
- >> loose the syncronisation with the blitter.
- >> (this also happens, when ECS-chipset is selected !!)
- >
- >Are you actually saying that on A500/2000 one cant access
- >chipram while blitting?
-
- Yep. That`s what some games used for syncronizing with the blitter.
- I know, that there`s a function to to this correctly, but this is of no help,
- if you bought the game and is simply doesn`t work.
-
-
- >I have always wondered why some people did no blitter waiting,
- >instead they did delay loops! What a brilliant idea!
-
- These people loose CPU-time. The dirty method some games use does not, every cycle
- to chip is used.. (on ECS)
-
-